Importing an empty staging table into SAS Activity-Based Management causes all non-empty staging tables with the same mapping to fail.

For example, if your import includes 3 DimensionMember tables that are named DimensionMember1, DimensionMember2 and DimensionMember3 (all are mapped to the DimensionMember target table during the map tables step of the SAS Activity-Based Management Import Data Wizard) and DimensionMember1 and DimensionMember2 tables have valid entries but the DimensionMember3 table is empty, then the import will fail. The empty DimensionMember3 table causes non-empty DimensionMember1 and DimensionMember2 table data to be ignored. An example import summary for such a scenario is shown below:

   Parcel Express Data Import Summary

   Fatal Errors
   Total Number of Fatal Errors: 0

   Errors
   Total Number of Errors: 1962

   Description: Attribute does not exist Count: 1
   1. 'Stage 1 Resources' on row 1 of table Model/MODEL

   Description: Dimension member does not exist Count: 1961
   1. 'Los Angeles' for dimension 'Reg' on row 1 of table Account/ACCOUNT
   2. 'Customer Service' for dimension 'Org' on row 1 of table Account/ACCOUNT
   3. 'Resolve Customer Complaints' for dimension 'Act' on row 1 of table Account/ACCOUNT
   4. Et cetera

   Warnings
   Total Number of Warning: 7

   Description: This name is greater than 12 characters and may be truncated when it
   appears in OLAP cubes. Count: 7

Although the DimensionMember table was referenced in this example, the results would be the same if other staging tables were empty and included in an import.

To circumvent this issue, exclude blank staging tables as source tables at the map tables step of the SAS Activity-Based Management Import Data Wizard.

Operating System and Release Information